Method, server and client for aggregating microblog single message

ABSTRACT

Embodiments of the application provide a method, server, client and system for aggregating a microblog single message. The method includes: triggering, by a user, to aggregate a microblog single message; and displaying a relaying process of the microblog single message for the user. The server includes: a receiving module, which is to receive a triggering message to aggregate a microblog single message from a client; an obtaining module, which is to obtain aggregation data of the microblog single message, according to the triggering message; a transmitting module, which is to transmit the aggregation data of the microblog single message obtained by the obtaining module to the client. Embodiments of the application also provide a corresponding client and system. By adopting the technical solution of the application, a user may clearly see a message relaying process. Thus, user satisfaction may be improved.

CROSS-REFERENCE TO RELATED APPLICATIONS

This is a continuation of International Patent Application No.PCT/CN2011/078449 filed Aug. 16, 2011, which claims the priority benefitof Chinese Patent Application No. CN 201010276111.7 filed Sep. 1, 2010,the entire respective disclosures of which are incorporated herein byreference.

TECHNICAL FIELD

The application relates to computer technologies, and more particularly,to a method, server, and client for aggregating a microblog singlemessage.

BACKGROUND OF THE INVENTION

Microblog products in our country are at an initial stage and used by alarge number of users. The microblog products have been widely used notonly in usual entertainment, but also in users' daily work.

In current mainstream microblog client software, microblog messages arepresented altogether on a QQ main panel in chronological order. When alarge number of users focused on the microblog messages, meanwhile homepage messages scroll and refresh faster, and then it is difficult topresent much information within relatively limited space on the mainpanel. Thus, displaying about details of a single message may be notclear and complete enough, which directly affect users' productexperience.

Besides, in existed microblog client software, since current user mayonly see messages about each user focused on by current user, currentuser doesn't learn relaying chain about each message. Since current userdoesn't focus on publishers of previous relaying chain, messages aboutprevious relaying chain are invisible to current user. For example, thewhole path of a single message chain is A-B-C-D-E, current user onlyfocuses on messages about E. Thus, current user may only see E, anddoesn't learn previous message chain.

Thus, in current mainstream microblog client software applications,users put forward higher requirements for ease of use, stability andsafety of microblog software. A user may hope to learn detailedinformation about a certain microblog message, and may hope to see therelaying process of the certain microblog message, so as to learn themicroblog relationship chain more conveniently.

SUMMARY OF THE INVENTION

In view of above, embodiments of the application provide a method,server, client and system for aggregating a microblog single message, toenable a user to access an independent page about an interested messagewith an entry, and enable the user to clearly see the relaying processabout the message.

An embodiment of the application provides a method for aggregating amicroblog single message, including:

-   -   receiving a user instruction;    -   sending a triggering message to aggregate the microblog single        message to a server, according to the user instruction;    -   receiving or obtaining aggregation data of the microblog single        message from the server; and    -   displaying the aggregation data of the microblog single message.

An embodiment of the application provides a server for aggregating amicroblog single message, including a receiving module, an obtainingmodule and a transmitting module, wherein

-   -   the receiving module is to receive a triggering message to        aggregate the microblog single message sent by a client;    -   the obtaining module is to obtain aggregation data of the        microblog single message, according to the triggering message;        and    -   the transmitting module is to transmit the aggregation data of        the microblog single message obtained by the obtaining module to        the client.

An embodiment of the application provides a client for aggregating amicroblog single message, including an interacting module, a datareceiving and obtaining module and a displaying module, wherein

-   -   the interacting module is to receive a user instruction, and        send a triggering message to aggregate the microblog single        message to a server according to the user instruction;    -   the data receiving and obtaining module is to receive or obtain        aggregation data of the microblog single message from the        server; and    -   the displaying module is to display the aggregation data of the        microblog single message.

By adopting the above technical solution of the application, a user atany page may be enabled to access an independent page about aninterested message with an entry. Besides, the user may be able to seethe message relaying process clearly, with the provided aggregationfunction about a single message. Meanwhile, the user may be enabled tolearn a relationship chain corresponding to the microblog moreconveniently. Thus, user experience may be improved.

BRIEF DESCRIPTIONS OF THE DRAWINGS

FIG. 1 is a flowchart illustrating a method for aggregating a microblogsingle message, in accordance with an embodiment of the application.

FIG. 2 is a flowchart illustrating a method for aggregating a microblogsingle message, in accordance with another embodiment of theapplication.

FIG. 3 is a flowchart illustrating a method for aggregating a microblogsingle message, in accordance with still another embodiment of theapplication.

FIG. 4 is a flowchart illustrating a method for downloading a thumbnail,when there is a picture in original text or message text of anindependent message page, in accordance with an embodiment of theapplication.

FIG. 5 is a flowchart illustrating a method for performing correspondingoperations on a thumbnail, when a user performs operations on thethumbnail, in accordance with an embodiment of the application.

FIG. 6 is a schematic diagram illustrating structure of a server foraggregating a microblog single message, in accordance with an embodimentof the application.

FIG. 7 is a schematic diagram illustrating structure of a server foraggregating a microblog single message, in accordance with anotherembodiment of the application.

FIG. 8 is a schematic diagram illustrating structure of a client foraggregating a microblog single message, in accordance with an embodimentof the application.

FIG. 9 is a schematic diagram illustrating structure of a client foraggregating a microblog single message, in accordance with anotherembodiment of the application.

FIG. 10 is a schematic diagram illustrating structure of a client foraggregating a microblog single message, in accordance with still anotherembodiment of the application.

FIG. 11 is a flowchart illustrating a method for aggregating a microblogsingle message, in accordance with another embodiment of theapplication.

EMBODIMENTS OF THE INVENTION

To make objectives, technical solutions and advantages of theapplication more clear, detailed descriptions about the application areprovided in the following accompanying with attached figures andspecific embodiments.

FIG. 1 is a flowchart illustrating a method for aggregating a microblogsingle message, in accordance with an embodiment of the application. Asshown in FIG. 1, the method includes the following blocks.

Block 101, a user triggers to aggregate a microblog single message.

When the user wants to see relaying process about a certain interestedmicroblog single message, the user may trigger to aggregate themicroblog single message.

Block 102, display the relaying process about the microblog singlemessage for the user.

FIG. 2 is a flowchart illustrating a method for aggregating a microblogsingle message, in accordance with another embodiment of theapplication. As shown in FIG. 2, the method includes the followingblocks.

Block 201, a user may double click on a specific microblog singlemessage from any of home page, @ page and guest page of microblogclient, to trigger aggregation of the microblog single message.Alternatively, the user may select a microblog single message, and clickon right button to select “aggregate”, so as to trigger the aggregationof the microblog single message.

Block 202, display relaying process of the microblog single message, byusing an independent message page carrying an entry of the microblogsingle message.

When the independent message page includes at least one message, displaysource of each message, that is, display each message is sent by whichterminal or user.

When the message includes a dialogue message, source and original textof the dialogue message may be displayed. The whole relaying chainreaching the user may also be viewed with the original text.

When the message includes a relaying message with or without comments,meanwhile number of the relaying message with or without comments islarger than or equal to a preset number, e.g., 10, the relaying originaltext and relaying number may be displayed.

When the message text, e.g., dialogue message, or relaying message withcomments, or relaying message without comments, includes a picture, thepicture thumbnail may be displayed. Meanwhile, the thumbnail may supportvarious operations, such as copy, open, etc.

FIG. 3 is a flowchart illustrating a method for aggregating a microblogsingle message, in accordance with another embodiment of theapplication. As shown in FIG. 3, the method includes the followingblocks.

Block 301, a user triggers to aggregate a microblog single message.

Block 302, determine whether the microblog single message requested tobe aggregated by the user is a relaying message or a dialogue message.When the microblog single message requested to be aggregated by the useris a relaying message, proceed with block 303; otherwise, proceed withblock 304.

Block 303, display relaying process of the relaying message for currentuser, according to time sequence of the relaying message being relayedby users focused on by current user, by using identifiers of usersfocused on by current user.

Specifically, the block may be implemented with the following two modes,but not limited to the two modes in the following.

The first mode, based on an identifier of a node corresponding to themicroblog single message requested to be aggregated, that is, therelaying message, search for identifier of each ancestor node of thenode. The ancestor node refers to father node of the node correspondingto the microblog single message, father node of the father node searchedout, until root node.

And then, based on all the ancestor nodes searched out, determine whichancestor node was focused on by current user. Display the relayingprocess of the relaying message for current user, according to timesequence of the relaying message being relayed by users focused on bycurrent user, by using identifiers of users focused on by current user.

The second mode is to store identifiers of all the users focused on bycurrent user, and messages relayed by all the users focused on bycurrent user, into a client.

In the messages relayed by each user focused on by current user, searchin sequence for the microblog single message requested to be aggregated,that is, the relaying message, according to time sequence of themessages being focused on by current user. When the relaying message issearched out from messages relayed by a user who was focused on bycurrent user, record identifier of the user who was focused on bycurrent user, until all the messages relayed by all the users focused onby current user have been traversed.

And then, display the relaying process of the relaying message forcurrent user, according to relaying time sequence and recordedidentifier of each user focused on by current user.

Block 304, display the relaying process of the dialogue message forcurrent user, according to relaying time sequence, by using identifierof each user who has relayed the dialogue message.

Block 305, determine whether any identifier of users focused on bycurrent user has been triggered once again, if yes, proceed with block306; otherwise, proceed with block 307.

Block 306, display the relaying process of the relaying message forcurrent user, by using identifier of each user who has relayed therelaying message.

Block 307, no longer display more detailed information.

FIG. 4 is a flowchart illustrating a method for downloading a thumbnail,when there is a picture in original text or message text of anindependent message page, during the process of displaying relayingprocess of a certain microblog single message for current user with theindependent message page, in accordance with an embodiment of theapplication. As shown in FIG. 4, the method includes the followingblocks.

Block 401, based on the method described with the embodiment shown inFIG. 2, during the process of displaying the relaying process of themicroblog single message with an independent message page, which carriesan entry of the microblog single message, when there is a picture inmessage text or original text of the independent message page, proceedwith block 402.

Block 402, determine whether a thumbnail corresponding to the picturehas been downloaded successfully, if yes, proceed with block 407;otherwise, proceed with block 403.

Block 403, place a default picture to replace the thumbnail to bedownloaded, add the picture to be downloaded to a downloading list,initiate a process animation, and then proceed with block 404.

Block 404, determine whether the thumbnail corresponding to the picturehas been downloaded successfully, if yes, proceed with block 405;otherwise, proceed with block 406.

Block 405, stop the process animation, remove the picture from thedownloading list, and proceed with block 407.

Block 406, place another default picture at the location of the originalthumbnail, e.g., display the picture indicating unsuccessfuldownloading.

Block 407, place the thumbnail successfully downloaded at the locationof the original thumbnail.

FIG. 5 is a flowchart illustrating a method for performing correspondingoperations on a thumbnail, when a user performs operations on thethumbnail, during the process of displaying relaying process of aspecific microblog message for the user with an independent messagepage, in which a picture is included in the message text or originaltext of the independent message page, in accordance with an embodimentof the application. As shown in FIG. 5, the method includes thefollowing blocks.

Block 501, when a user performs operations on a thumbnail, such as “viewan original picture”, “copy”, “save as”, record a correspondingoperation to be performed on current picture which has been selected bythe user recently.

Block 502, determine whether the original picture has been downloaded,if yes, proceed with block 507; otherwise, proceed with block 503.

Block 503, add a picture to be downloaded to a downloading list,initiate a process animation, and proceed with block 504.

Block 504, determine whether the picture has been downloadedsuccessfully, if yes, proceed with block 505; otherwise, proceed withblock 506.

Block 505, stop the process animation, and remove the picture from thedownloading list.

Block 506, place another default picture, and display unsuccessfuldownloading.

Block 507, perform corresponding operations, according to correspondingoperation to be performed on current picture, which are recorded inblock 501.

For example, when a user clicks on “view an original picture” with rightbutton, it is necessary to trigger the logic for downloading theoriginal picture. At this time, there may be a downloading animation forthe thumbnail corresponding to the picture. It should be noted that, atthis time, when network speed is relatively slow, the user may performoperations on the picture or other pictures more than once, such as“view an original picture”, “copy” and “save as”. Thus, new downloadingmay be triggered. To avoid new downloading unnecessary, the followingmodes may be employed.

For example, employ a mapping table within a program to store adownloading picture list, so as to shield repeated downloading of apicture. Meanwhile, employ another mapping table to store the finaloperation to be performed on the corresponding picture, which isrecorded in block 501. When picture downloading is finished, onlyperform the final operation. For example, when a user firstly selects“view an original picture”, and then immediately selects “save as”.Thus, the final operation is “save as”.

In the embodiment, when the user selects “view an original picture”,call a function to run an external program. In a windows system, such asWindows XP system, Windows 2000 system, ShellExecute function may becalled. Take the Windows XP system for an example, when there is nodefault picture viewer for the picture, return value of the calledShellExecute function will be smaller than 32. At this time, based onthe return value of the ShellExecute function, “open mode” selection boxmay be opened, to facilitate the user to select a picture viewer to viewthe picture.

FIG. 6 is a schematic diagram illustrating structure of a server foraggregating a microblog single message, in accordance with an embodimentof the application. As shown in FIG. 6, a server 601 includes areceiving module 602, an obtaining module 603 and a transmitting module604.

The receiving module 602 is to receive a triggering message to aggregatea microblog single message from client 701.

The obtaining module 603 is to obtain aggregation data of the microblogsingle message based on the triggering message.

The transmitting module 604 is to transmit the aggregation data of themicroblog single message obtained by the obtaining module 603 to theclient 701, to facilitate the client 701 to display for the user.

FIG. 7 is a schematic diagram illustrating structure of a server foraggregating a microblog single message, in accordance with anotherembodiment of the application. As shown in FIG. 7, in addition to thereceiving module 602, the obtaining module 603 and the transmittingmodule 604, the server 601 further includes a storing module 605.

Functions of the receiving module 602 are same as that in the embodimentillustrated with FIG. 6, which are not repeated here.

The storing module 605 is to store aggregation data of the microblogsingle data. The aggregation data of the microblog single messageincludes information about a node corresponding to the microblog singlemessage and information about ancestor node thereof. The ancestor noderefers to father node of the node corresponding to the microblog singlemessage, father node of the father node, until root node.

The obtaining module 603 is further to obtain an identifier of eachancestor node of the node corresponding to the microblog single message.

The transmitting module 604 is further to, transmit identifier of thenode corresponding to the microblog single message and the identifier ofeach ancestor node thereof, both of which are obtained by the obtainingmodule 603, to the client 701, so as to display for the user.

That is, for each relayed microblog message, the server storesidentifier information about father node of the node corresponding tothe microblog message, identifier information about father node of thefather node, until identifier information about the root node. Whenaggregation is necessary, current node may be taken as a basis to obtainall the nodes in a father chain upwards, so as to form an aggregationchain of the single message.

Definitely, other modes may be employed by a server for aggregating amicroblog single message. For example, a server may be formed by anaccess layer for relaying and aggregating a single message, a module foraggregating and performing logic process on a single message, a datacache layer for aggregating a single message, and a microblog datastoring module (not shown in Figure).

The access layer for relaying and aggregating a single message is incharge of unified accessing when visited by upper layer terminal, so asto avoid illegal visit. Meanwhile, the access layer for relaying andaggregating a single message is also to shield lower layer module foraggregating and performing logic process on a single message, to enabledeployment of processing modules to be relatively independent. Whenreceiving a triggering message to aggregate a specific microblogmessage, which is sent by a client, e.g., QQ client or other client, theaccess layer for relaying and aggregating a single message may determinewhether the triggering message is sent by a designated protocol; if yes,send the triggering message to the module for aggregating and performinga logic process on a single message.

Subsequently, based on the triggering message received, the module foraggregating and performing a logic process on a single message mayobtain father node identifier (ID) from the microblog data storingmodule, according to ID of the node corresponding to the microblogsingle message requested to be aggregated, and then, obtain father nodeID of the father node ID which has already been obtained, until ID of aroot node has been obtained. Thus, the whole aggregation chain expectedby a service layer may be obtained after pulling many times. Meanwhile,to ensure pulling efficiency, concurrent and asynchronous processes maybe executed. Partial intermediate data and result data may be buffered,to avoid putting too much pressure on the microblog data storing module.

FIG. 8 is a schematic diagram illustrating structure of a client foraggregating a microblog single message, in accordance with an embodimentof the application. As shown in FIG. 8, client 701 includes aninteracting module 702, a data receiving and obtaining module 703, and adisplaying module 704.

The interacting module 702 is to interact with a user, send a triggeringmessage to aggregate a microblog single message to server 601 accordingto user instruction, and send a message to the data receiving andobtaining module 703 to indicate to receive or obtain aggregation dataof the microblog single message from the server.

The data receiving and obtaining module 703 is to receive or obtain theaggregation data of the microblog single message from server 601,according to the message sent by the interacting module 702.

The displaying module 704 is to display the aggregation data of themicroblog single message, which is obtained by the data receiving andobtaining module 703, for the user.

To enable server load as low as possible when service quality issatisfied, under the circumstances that a relaying chain of a message isrelatively long, when pulling all the messages about the relaying chainat a time, huge load may be brought to the server. Take clientapplication scenario into consideration, the strategy of batch andpulling many times may be employed in the embodiment of the application.The data receiving and obtaining module 703 is to receive or obtainpreset number of messages from the aggregation data of the microblogsingle message stored in the server 601 at a time. Take into account theminimum byte number length limitation of a network exchange betweenclient and server in a network, as well as an average length of arelayed and aggregated message, 15 relayed and aggregated messages areallowed to be pulled at a time in the embodiment. When a user has seencurrent page and scrolled down to the bottom, next batch pulling processmay be triggered, until a preset number of messages have been pulled,for example, after pulling 120 messages, no longer to pull as a responseto triggering event at the bottom of scroll bar. Instead, prompt theuser to view more, so as to enable the user to manually click on to jumpto corresponding webpage.

FIG. 9 is a schematic diagram illustrating structure of a client foraggregating a microblog single message, in accordance with anotherembodiment of the application. As shown in FIG. 9, in addition to theinteracting module 702, the data receiving and obtaining module 703, thedisplaying module 704, the client 701 further includes a first datastoring module 705, a second data storing module 706, a determiningmodule 707 and an establishing module 708.

Functions of the interacting module 702 as well as the data receivingand obtaining module 703 are same as that in the embodiment illustratedwith FIG. 8, which are not repeated here.

The first data storing module 705 is to store aggregation data of amicroblog single message received or obtained by the data receiving andobtaining module 703 from the server 601. The aggregation data includesan identifier of a node corresponding to the microblog single messageand identifier of each ancestor node thereof. The ancestor node includesfather node of the node corresponding to the microblog single message,father node of the father node, until a root node.

When the microblog single message is a relaying message, the second datastoring module 706 is to store an identifier of each user focused on bycurrent user according to time sequence.

When the microblog single message is a relaying message, the determiningmodule 707 is to determine, which of the identifier of the nodecorresponding to the relaying message and identifier of each ancestornode thereof stored in the first data storing module 705, is stored inthe second data storing module 706, and to send each node identifierstored in the second data storing module 706 to the displaying module704.

After the first data storing module 705 stores the aggregation data ofthe microblog single message received or obtained by the data receivingand obtaining module 703 from the server 601, that is, obtain datarelated with an independent message page to be established in thefollowing, the establishing module 708 is to establish an independentmessage page with an entry of the microblog single message.

When the microblog single message is a relaying message, the displayingmodule 704 is further to, receive the node identifiers stored in thesecond data storing module 706 which are sent by the determining module707, and display the relaying process of the relaying message relayed byusers focused on by current user for current user according to relayingtime sequence, by using the independent message page established by theestablishing module 708 and node identifiers. When the microblog singlemessage is a relayed dialogue message, the displaying module 704 isfurther to, display the identifier of the node corresponding to themicroblog single message and an identifier of each ancestor node thereoffor current user according to relaying sequence, based on theaggregation data stored in the first data storing module 705, by usingthe independent message page established by the establishing module 708.

Specifically, when the independent message page includes at least onemessage, the displaying module 704 is further to display source of eachmessage, e.g., the message is sent by which terminal or user. When themessage includes a dialogue message, the displaying module 704 isfurther to display original text of the dialogue message. When themessage includes a relaying message with or without comments, and whenrelaying number of the relaying message with or without comments islarger than or equal to a preset number, the displaying module 704 isfurther to display relaying number and original relaying contents. Whenthere is neither relaying message nor dialogue message in the message,the displaying module 704 is only to display detailed contents of themessage. When message text, such as, dialogue message, relaying messagewith or without comments, or message original text, includes a picture,the displaying module 704 is to further display a thumbnail of thepicture. The thumbnail here may support various operations, such as,copy, open, save as, view, which may refer to foregoing embodimentsillustrated with FIG. 4 and FIG. 5, which are not repeated here.

When the microblog single message is a relaying message, the client 701may also be implemented with the following modes. For example, theclient 701 may be configured to save identifiers of all the usersfocused on by current user, and messages relayed by all the usersfocused on by current user.

Search in all the messages relayed by users focused on by current userfor the microblog single message requested to be aggregated, that is,the relaying message, according to time sequence of each user focused onby current user. When the relaying message is searched out from messagesrelayed by a certain user focused on by current user, record identifierof the certain user, until all the messages relayed by all the usersfocused on by current user have been traversed.

And then, display the relaying process of the relaying message relayedby each user focused on by current user, according to relaying sequence,and by using recorded identifier of each user focused on by currentuser.

In the processes for designing the client and server in the embodimentsof the application, loosely coupled structure and server load as low aspossible are aimed to be achieved. To obtain a loosely coupled codedesign framework, design ideas of hierarchical module are employed, toencapsulate related logic functions into one layer. An abstract datastructure, such as an interface or a pure virtual function, may beemployed to express relationship among different layers, to enable codereusability to be better.

Based on foregoing design concept, the client 701 may also beimplemented with other modes. For example, divide the client 701 into apresentation layer, a service logic layer and a data layer (which arenot shown in the Figure). The presentation layer therein is toencapsulate interactions with users. The server logic layer, which istaken as a core function layer of the client, is mainly in charge offunctional logic process and state storage. The data layer is to obtaindata from a server, such as pull data, and organize the obtained data.

FIG. 10 is a schematic diagram illustrating structure of a client foraggregating a microblog single message, in accordance with anotherembodiment of the application. The differences between FIG. 10 and FIG.9 are as follows. In FIG. 10, the first data storing module 705 furtherincludes a picture storing module 7051, the data receiving and obtainingmodule 703 further includes a picture pulling module 7031.

Functions of each of the interacting module 702, the second data storingmodule 706, the determining module 707 and the establishing module 708in FIG. 10 are respectively same as that in FIG. 9, which are notrepeated here.

When message text includes a thumbnail, in addition to displaying theaggregation data of the microblog single message obtained by the datareceiving and obtaining module 703 for current user, the displayingmodule 704 in FIG. 10 is further to display the thumbnail successfullydownloaded. The specific descriptions are as follows.

When the message text, such as dialogue message, relaying message withor without comments, or the message original text includes a thumbnail,the picture pulling module 7031 is to determine whether the picturestoring module 7051 has stored the thumbnail successfully downloaded. Ifyes, the displaying module 704 is further to display the thumbnailsuccessfully downloaded; otherwise, the picture pulling module 7031 isfurther to download the thumbnail from the server 601, add the pictureto be downloaded to a downloading list, and initiate a processanimation. When the downloading is successful, the displaying module 704is to stop the process animation, remove the picture from thedownloading list, and send the thumbnail successfully downloaded to thepicture storing module 7051 to be stored.

An embodiment of the application also provides a system for aggregatinga microblog single message, which is formed by the server 601 and theclient 701 (which are not shown in Figure). Structure of the server 601may refer to FIG. 6 and FIG. 7. Structure of the client 701 may refer toFIG. 8, FIG. 9 and FIG. 10. It should be noted that, structure of theserver 601 is not limited to the two kinds of structures illustratedwith FIG. 6 and FIG. 7. Structure of the client 701 is also not limitedto the two structures illustrated with FIG. 8 and FIG. 9

FIG. 11 is a flowchart illustrating a method for aggregating a microblogsingle message, in accordance with another embodiment of theapplication. As shown in FIG. 11, blocks 1101, 1102, 1103, 1105 and 1107are respectively same as blocks 301, 302, 303, 305 and 307 in FIG. 3,which are not repeated here.

As shown in FIG. 11, after executing block 1102, when determining themicroblog single message is a dialogue message, proceed with block 1104.When the dialogue message has not been relayed, display source andoriginal text of the dialogue message. When the dialogue message hasbeen relayed, display relaying process of the dialogue message forcurrent user according to relaying time sequence, by using identifier ofeach user who has relayed the dialogue message.

Regarding block 1105, as a supplement, computer may wait for doubleclick of current operating user, or triggering any of identifiers of allthe users focused on by current user with any other mode. Whendetermining any of identifiers of all the users focused on by currentuser has been triggered, proceed with block 1106. That is, displaydetailed information about the relaying message relayed by the usercorresponding to the triggered user identifier with an independentmessage page, e.g., user account, relaying time, relaying location, howmany users have relayed the message after being relayed by the user, andprovide an entry for current user to execute further operations, e.g.,copy, relay, etc.

The foregoing is only preferred embodiments of the application, whichare not used for limiting the application. Any change or substitutionwithin the technical scope disclosed by the application, which is easilyoccurred to a person having ordinary skill in the art, should be coveredby the protection scope of the application. Thus, protection scope ofthe application should be determined by the claims.

The invention claimed is:
 1. A method for aggregating a microblog single message, comprising: receiving a user instruction; sending a triggering message to aggregate the microblog single message to a server, according to the user instruction; receiving or obtaining aggregation data of the microblog single message from the server; and displaying the aggregation data of the microblog single message; wherein displaying the aggregation data of the microblog single message comprises: displaying the relaying process of the microblog single message, by using an independent message page with an entry of the microblog single message; wherein when the microblog single message comprises a relaying message, displaying the aggregation data of the microblog single message comprises, displaying the relaying process of the relaying message, according to relaying time sequence of the relaying message being relayed by each user focused on by the user, by using an identifier of each user focused on by the user; and wherein when the microblog single message comprises a relayed dialogue message, displaying the aggregation data of the microblog single message comprises, displaying the relaying process of the dialogue message according to relaying time sequence, by using an identifier of each user who has relayed the dialogue message.
 2. The method according to claim 1, wherein when displaying the relaying process of the relaying message for the user, according to the relaying time sequence of the relaying message being relayed by each user focused on by the user, by using the identifier of each user focused on by the user, the method further comprises: when triggering any of identifiers of all the users focused on by the user, displaying the relaying process of the relaying message for the user, according to an identifier of each user who has relayed the relaying message.
 3. The method according to claim 1, wherein when displaying the relaying process of the relaying message for the user, according to the relaying time sequence of the relaying message being relayed by each user focused on by the user, by using the identifier of each user focused on by the user, the method further comprises: when triggering any of identifiers of users focused on by the user, displaying information about the relaying message relayed by a user corresponding to the triggered user identifier for the user.
 4. A client for aggregating a microblog single message, comprising a processor, a memory, and an interacting module, a data receiving and obtaining module as well as a displaying module, wherein the interacting module is to interact with a user, and send a triggering message to aggregate the microblog single message to a server according to the user instruction; the data receiving and obtaining module is to obtain or receive information about the aggregation data of the microblog single message from the server, according to an instruction sent by the interacting module, receive or obtain the aggregation data of the microblog single message from the server according to the information; and the displaying module is to display the aggregation data of the microblog single message for the user; wherein the client further comprises a first data storing module, a second data storing module, a determining module and an establishing module, the first data storing module is to store the aggregation data of the microblog single message received or obtained by the data receiving and obtaining module, wherein the aggregation data comprises an identifier of a node corresponding to the microblog single message and an identifier of each ancestor node of the node, the ancestor node comprises a father node of the node corresponding to the microblog single message, upwards until a root node; the second data storing module is to store an identifier of each user focused on by the user according to time sequence, when the microblog single message is a relaying message; the determining module is to determine, when the microblog single message is the relaying message, which of the identifier of the node corresponding to the relaying message and the identifier of each ancestor node of the node stored in the first data storing module, is stored in the second data storing module, and send a node identifier stored in the second data storing module to the displaying module; the establishing module is to establish an independent message page with an entry of the microblog single message, when the first data storing module has stored the aggregation data of the microblog single data received or obtained by the data receiving and obtaining module from the server; and when the microblog single message is the relaying message, the displaying module is further to receive the node identifier stored in the second data storing module sent by the determining module, display a relaying process of the relaying message relayed by each user focused by the user for the user, according to relaying time sequence, by using the node identifier and the independent message page established by the establishing module; when the microblog single message is a relayed dialogue message, the displaying module is further to receive the node identifier stored in the second data storing module sent by the determining module, display a relaying process of the relaying message relayed by each user focused by the user, according to relaying time sequence, by using the node identifier and the independent message page established by the establishing module; when the microblog single message is a relayed dialogue message, the displaying module is to display the identifier of the node corresponding to the microblog single message and the identifier of each ancestor node of the node for the user, according to relaying time sequence and the aggregation data stored in the first data storing module, by using the independent message page established by the establishing module, wherein the interacting module, the displaying module, the first data storing module, the second data storing module, the determining module, and the establishing module are stored on the memory.
 5. The client according to claim 4, wherein when the displaying module displays the relaying process of the relaying message relayed by each user focused on by the user for the user, according to the relaying time sequence, by using the node identifier and the independent message page established by the establishing module, the displaying module is further to, when any node identifier is triggered, display the relaying process of the relaying message for the user, by using the node identifier which has relayed the relaying message and is stored in the first data storing module; or when any node identifier is triggered, the displaying module is to display information about the relaying message which is relayed by a user corresponding to the triggered node identifier for the user.
 6. The client according to claim 4, wherein the first data storing module further comprises a picture storing module, the data receiving and obtaining module further comprises a picture pulling module; when message text comprises a thumbnail, the picture pulling module is to determine whether the picture storing module has stored the thumbnail successfully downloaded; when the picture storing module has stored the thumbnail successfully downloaded, the displaying module is further to display the thumbnail successfully downloaded; when the picture storing module doesn't store the thumbnail successfully downloaded, the picture pulling module is further to download the thumbnail from the server, add the thumbnail to be downloaded to a downloading list, initiate a process animation; when downloading is successful, the picture pulling module is further to stop the process animation, remove the thumbnail from the downloading list, and send the thumbnail successfully downloaded to the picture storing module to be stored, to facilitate the displaying module to display for the user.
 7. A method for aggregating a microblog single message, comprising: triggering, by a user, to aggregate the microblog single message; and displaying a relaying process of the microblog single message for the user; wherein displaying the relaying process of the microblog single message for the user comprises: displaying the relaying process of the microblog single message for the user, by using an independent message page with an entry of the microblog single message; wherein displaying the relaying process of the microblog single message for the user, by using the independent message page with the entry of the microblog single message, comprises: when the independent message page comprises a message, displaying source of the message; when the message includes a dialogue message, further displaying original text of the dialogue message; when the message includes a relaying message with or without comments, and relaying number of the relaying message with or without comments is larger than or equal to a preset number, further displaying relaying original text and the relaying number; and when the dialogue message, or the relaying message with comments, or the relaying message without comments comprises a picture, further displaying a thumbnail of the picture.
 8. The method according to claim 7, wherein when the dialogue message, or the relaying message with comments, or the relaying message without comments comprises the picture, further displaying the thumbnail of the picture comprises: when the thumbnail has been downloaded, displaying the thumbnail successfully downloaded; and when the thumbnail has not been downloaded, add the thumbnail to be downloaded to a downloading list, and initiate a process animation; when the downloading is successful, stop the process animation, remove the thumbnail from the downloading list, and display the thumbnail successfully downloaded.
 9. The client according to claim 4, wherein when the independent message page comprises a message, the displaying module is further to display source of the message; when the message comprises a dialogue message, the displaying module is further to display original text of the dialogue message; when the message comprises a relaying message with or without comments, and relaying number of the relaying message with or without comments is larger than or equal to a preset number, the displaying module is further to display relaying original text and the relaying number; when the dialogue message, or the relaying message with comments, or the relaying message without comments comprises a picture, the displaying module is further to display a thumbnail of the picture. 